Summary

Adds a new terminal SKIPPED status to the CDK's async job framework. When an API indicates a job has no data to return (e.g., Amazon SP-API's CANCELLED status), connectors can now map it to skipped instead of forcing it into failed or timeout — both of which trigger wasteful retries (up to 3x).

Behavior: SKIPPED partitions free their job budget and are silently dropped — no records are fetched, no retries are attempted, no errors are raised.

Backward-compatible: The skipped key in AsyncJobStatusMap is optional (Optional[List[str]] = None). Existing connector manifests that don't declare it continue to work unchanged.

Files changed:

• status.py — new SKIPPED enum member (terminal)
• job_orchestrator.py — partition status aggregation, _process_skipped_partition, match case
• declarative_component_schema.yaml — optional skipped property on AsyncJobStatusMap
• declarative_component_schema.py — Pydantic model field
• model_to_component_factory.py — status mapping + scoped None-guard that only allows None for optional fields (skipped); required fields raise ValueError if None
• test_job_orchestrator.py — 6 new tests (partition status combos + orchestrator behavior)

Review & Testing Checklist for Human

• Pydantic model vs codegen: declarative_component_schema.py appears to be auto-generated from the YAML schema. Confirm whether this manual edit will survive the next codegen run, or if the YAML change alone is sufficient. Run /poe build to regenerate and verify.
• Partition status priority logic (AsyncPartition.status): Verify the ordering of checks is correct — particularly that {COMPLETED, SKIPPED} resolves to COMPLETED (not SKIPPED), and that SKIPPED doesn't shadow the FAILED/TIMED_OUT wildcard retry paths. The subset check statuses <= {AsyncJobStatus.COMPLETED, AsyncJobStatus.SKIPPED} is the key line.
• Scoped None guard in _create_async_job_status_mapping: The guard only allows None for fields in _OPTIONAL_ASYNC_STATUS_FIELDS (currently {"skipped"}). Required fields (running, completed, failed, timeout) raise ValueError if None. This is not directly unit-tested — consider adding a test.
• Existing tests that enumerate all AsyncJobStatus values (e.g., test_given_one_failed_job_when_status_then_return_failed creates one job per enum value): These now include a SKIPPED job. Verify the priority expectations still hold with the extra status in the mix.

Suggested test plan: Use the /test slash command to run connector tests with this CDK branch. Then manually verify with a connector that uses async jobs (e.g., source-amazon-seller-partner) by pinning the CDK to this branch and confirming SKIPPED-mapped statuses produce no records and no retries.

Notes

• Motivated by oncall#11837: Amazon SP-API's CANCELLED means "no data to return" but the CDK currently forces it into timeout/failed, causing 3 wasteful retries that burn rate-limit budget and can cascade into FATAL errors.
• Companion connector PR: airbytehq/airbyte#76093 — once this CDK change ships, the connector can switch from timeout: [CANCELLED] to skipped: [CANCELLED].

Link to Devin session: https://app.devin.ai/sessions/45ba0c82b9654fbb8ce037502492bd3d